Help

Composite Master Key


This document details how KeePass locks its databases.

KeePass stores your passwords securely in an encrypted file (database). This database is locked with a master password, a key file and/or the current Windows account details. To open a database, all key sources (password, key file, ...) are required. Together, these key sources form the Composite Master Key.

KeePass does not support keys being used alternatively, i.e. it's not possible that you can open your database using a password or a key file. Either use a password, a key file, or both at once (both required), but not interchangeably.


Info  Master Passwords

If you use a master password, you only have to remember one password or passphrase (which should be good!) to open your database. KeePass features protection against brute-force and dictionary attacks on the master password, read the security information page for more about this.

If you forget this master password, all your other passwords in the database are lost, too. There isn't any backdoor or a key which can open all databases. There is no way of recovering your passwords.


Info  Key Files

You don't even have to remember a long, complicated master passphrase. The database can also be locked using a key file. A key file is basically a master password in a file. Key files are typically stronger than master passwords, because the key can be a lot more complicated; however it's also harder to keep them secret.

The point of a key file is that you have something to authenticate with (in contrast to master passwords, where you know something), for example a file on a USB stick. The key file content (i.e. the key data contained within the key file) needs to be kept secret. The point is not to keep the location of the key file secret — selecting a file out of thousands existing on your hard disk basically doesn't increase security at all (it's very easy for malware/attackers to find out the correct file, for example by observing the last access times of files). Trying to keep the key file location secret is security by obscurity, i.e. not really effective.

KeePass can generate key files for you, however you can also use any other, already existing file (like JPG image, DOC document, etc.).

In order to use an existing file as key file, click the 'Browse' button in the master key creation dialog.

Info  Windows User Account


KeePass can make the database dependent on the current Windows user account. If you enable this option, you can only open the database when you are logged in as the same Windows user when creating the database.

You can still change the password of the Windows user account freely. This does not affect the KeePass database.

Be very careful with using this option. If your Windows user account gets deleted, you won't be able to open your KeePass database anymore. Also, when using this option at home and your computer breaks (hard disk damaged), it is not enough to just create a new Windows account on the new installation with the same name and password; you need to copy the complete account (i.e. SID, ...). This is not a simple task, so if you don't know how to do this, it is highly recommended that you don't enable this option.

If you decide to use this option, it is highly recommended not to rely on it exclusively, but to additionally use one of the other two options (password or key file).

Triggers allow you to automatically export the database when you save. Saving in XML format provides a useful backup, but the export is in plain text, not encrypted. See the Trigger Examples for more details.

Protection using user accounts is unsupported on Windows 98 / ME.

Info  For Administrators: Specifying Minimum Properties of Master Keys

Administrators can specify a minimum length and/or the minimum estimated quality that master passwords must have in order to be accepted. You can tell KeePass to check these two minimum requirements by adding/editing appropriate definitions in the INI/XML configuration file.

The contents of the MinimumLength node in Security/MasterPassword can contain the minimum master password length in characters. For example, by setting the contents to 10, KeePass will only accept master passwords that have at least 10 characters.

The contents of the MinimumQuality node in Security/MasterPassword can contain the minimum estimated quality in bits that master passwords must have. For example, by setting the contents to 32, only master passwords with an estimated quality of at least 32 bits will be accepted.

By specifying KeyCreationFlags and/or KeyPromptFlags (in the UI node), you can force states (enabled, disabled, checked, unchecked) of key source controls in the master key creation and prompt dialogs. These values can be bitwise combinations of one or more of the following flags:

Flag (Hex)Flag (Dec)Description
0x00Don't force any states (default).
0x11Enable password.
0x22Enable key file.
0x44Enable user account.
0x88Enable 'hide password' button.
0x100256Disable password.
0x200512Disable key file.
0x4001024Disable user account.
0x8002048Disable 'hide password' button.
0x1000065536Check password.
0x20000131072Check key file.
0x40000262144Check user account.
0x80000524288Check 'hide password' option/button.
0x100000016777216Uncheck password.
0x200000033554432Uncheck key file.
0x400000067108864Uncheck user account.
0x8000000134217728Uncheck 'hide password' option/button.

For example, if you want to enforce using the user account option, you could check and disable the control (such that the user can't uncheck it anymore) by specifying 263168 as value (0x40000 + 0x400 = 0x40400 = 263168).